Skip to content

[DNR DNM] CI for juju 3.6, ck8s 1.34-classic, track-1#932

Draft
nrobinaubertin wants to merge 8 commits into
track/1from
ci-ck8s-3.6j-t1
Draft

[DNR DNM] CI for juju 3.6, ck8s 1.34-classic, track-1#932
nrobinaubertin wants to merge 8 commits into
track/1from
ci-ck8s-3.6j-t1

Conversation

@nrobinaubertin

Copy link
Copy Markdown
Contributor

Overview

Rationale

Juju Events Changes

Module Changes

Library Changes

Checklist

@nrobinaubertin nrobinaubertin changed the base branch from 2/main to track/1 August 7, 2025 17:01
@amandahla

Copy link
Copy Markdown
Contributor

Considering what we discussed about using latest versions for CI and also considering that we should use k8s instead of microk8s, could you update this PR and the one for 2/main branch with:

with:
      channel: 1.34-classic/stable
      juju-channel: 3/stable
      self-hosted-runner: true
      self-hosted-runner-label: "xlarge"
      use-canonical-k8s: true
      provider: 'k8s'

So we can make it everything right: use k8s, latest versions and also use self-hosted-runners.

wdyt

@nrobinaubertin nrobinaubertin changed the title [DNR DNM] CI for juju 3.1, ck8s 1.32-classic, track-1 [DNR DNM] CI for juju 3.6, ck8s 1.34-classic, track-1 Sep 8, 2025
@nrobinaubertin

Copy link
Copy Markdown
Contributor Author

So we can make it everything right: use k8s, latest versions and also use self-hosted-runners.

I made the change but decided to pin the version of juju to the minor: I feel like this is more correct if we want to test for a particular version of it (rather than just following the major)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants